-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to output messages in JSON format #288
Conversation
Signed-off-by: Addisu Z. Taddese <[email protected]>
Codecov Report
@@ Coverage Diff @@
## ign-transport10 #288 +/- ##
===================================================
- Coverage 89.10% 89.05% -0.06%
===================================================
Files 51 51
Lines 4765 4779 +14
===================================================
+ Hits 4246 4256 +10
- Misses 519 523 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just minor comments.
Signed-off-by: Addisu Z. Taddese <[email protected]>
Signed-off-by: Addisu Z. Taddese <[email protected]>
The windows warnings are also in the |
This pull request has been mentioned on Gazebo Community. There might be relevant details there: https://community.gazebosim.org/t/new-ignition-releases-2022-03-25-fortress-edifice-citadel/1343/1 |
🎉 New feature
Summary
This adds a command line option
--json-output
to allow output in JSON format instead of Protobuf's defaultDebugString
format. This would useful for manipulating message output with tools likejq
. For example, if we wanted to extract just thex
component of aPose
message, we could doign topic -e --json-output -t /pose_topic | jq '.position.x'
Test it
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.